In newer versions of Minecraft, the --server and --port launch arguments have been replaced with a single --quickPlayMultiplayer option. This PR adds support for the new option while maintaining backward compatibility.

Changes

• Added quickPlayMultiplayer option to LaunchOption interface for direct server connection using the new format
• Updated argument generation logic to use --quickPlayMultiplayer when provided, with precedence over legacy --server/--port options
• Added createQuickPlayMultiplayer() helper function to easily format server IP and port into the required string format
• Maintained full backward compatibility with existing server: { ip, port } option
• Added comprehensive tests covering all new functionality and edge cases
• Updated documentation with usage examples and migration guidance

Usage Examples

import { launch, createQuickPlayMultiplayer } from "@xmcl/core"

// New quickPlayMultiplayer option
await launch({
  version: '1.20.1',
  gamePath: '/path/to/.minecraft',
  javaPath: '/path/to/java',
  quickPlayMultiplayer: 'play.hypixel.net:25565'
})

// Helper function for easy formatting
await launch({
  version: '1.20.1', 
  gamePath: '/path/to/.minecraft',
  javaPath: '/path/to/java',
  quickPlayMultiplayer: createQuickPlayMultiplayer('mc.example.com', 8080)
})

// Legacy server option still works
await launch({
  version: '1.20.1',
  gamePath: '/path/to/.minecraft', 
  javaPath: '/path/to/java',
  server: { ip: 'play.hypixel.net', port: 25565 }
})

Migration

For users wanting to use the new format:

• Replace server: { ip: 'example.com', port: 25565 } with quickPlayMultiplayer: 'example.com:25565'
• Or use the helper: quickPlayMultiplayer: createQuickPlayMultiplayer('example.com', 25565)

Fixes #320.

💬 Share your feedback on Copilot coding agent for the chance to win a $200 gift card! Click here to start the survey.